Battery charger for a transaction card

ABSTRACT

Examples described herein describe a battery charger for a transaction card. According to some implementations, a charging device may detect a transaction card is received within a charging slot when an integrated circuit (IC) chip of the transaction card is in contact with a charging terminal; request a user device to provide power to charge the transaction card via the charging terminal, wherein the user device is communicatively coupled to the charging terminal; receive the power from the user device; and provide the power to the transaction card to charge a battery of the transaction card.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.16/241,484, filed Jan. 7, 2019 (now U.S. Pat. No. 10,579,917), which isa continuation of U.S. patent application Ser. No. 16/119,762, filedAug. 31, 2018 (now U.S. Pat. No. 10,176,414), which are incorporatedherein by reference.

BACKGROUND

Transaction cards (e.g., credit cards, debit cards, gift cards,automated teller machine (ATM) cards, rewards cards or client loyaltycards, and/or the like) and/or devices (e.g., a smart transaction card,a smartphone, and/or the like) may be used in transactions to pay forproducts or services at transaction terminals (e.g., point of sale (PoS)terminals) of individuals or businesses engaged in the sale of goods orservices. The transaction cards may include an integrated circuit (IC)chip to improve security with respect to use of the transaction card.

SUMMARY

According to some implementations, a method may include detecting atransaction card is received within a charging slot; determining that anamount of remaining power in a charger battery is less than a firstthreshold level; requesting a user device to provide power to charge thetransaction card based on determining the amount of remaining power inthe charger battery is less than the first threshold level, wherein theuser device is communicatively coupled to the charging device via adevice interface of the user device and a charging jack of the chargingdevice; receiving the power from a battery of the user device; andproviding, via the charging device, the power to the transaction card tocharge a battery of the transaction card via a charging terminal of thecharging device.

According to some implementations, a charging device may include acharging slot; a charging terminal; a user device holder to hold a userdevice; a charging jack that is to be inserted within a device interfaceof the user device when the user device is in the user device holder;one or more memories; and one or more processors, communicativelycoupled to the one or more memories, to: detect that a transaction cardis received within the charging slot; draw power from a battery of theuser device to provide power to the transaction card; and provide thepower to the transaction card via an integrated circuit (IC) chip thatis in contact with the charging terminal.

According to some implementations, a non-transitory computer-readablemedium may store instructions that, when executed by one or moreprocessors, cause the one or more processors to: detect a transactioncard is received within a charging slot when an integrated circuit (IC)chip of the transaction card is in contact with a charging terminal;request a user device to provide power to charge the transaction cardvia the charging terminal, wherein the user device is communicativelycoupled to the charging terminal; receive the power from the userdevice; and provide the power to the transaction card to charge abattery of the transaction card.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1-4 are diagrams of example implementations described herein.

FIG. 5 is a diagram of an example environment in which systems and/ormethods, described herein, may be implemented.

FIG. 6 is a diagram of example components of one or more devices of FIG.5.

FIGS. 7-9 are flow charts of example processes associated with a batterycharger for a transaction card.

DETAILED DESCRIPTION

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

In some instances a transaction card (e.g., credit cards, debit cards,ATM cards, gift cards, loyalty cards, security key cards, and/or thelike) may include an electronic circuit with components that are poweredby a battery. For example, the battery may provide power to one or morecommunication interfaces, one or more processors, one or more userinterfaces, one or more memories, one or more storage components, and/orthe like of the transaction card. In some cases, the battery of thetransaction card can be charged when inserted into a transactionterminal (e.g., a point of sale (POS) terminal, a security terminal,and/or the like). As such, the battery of the transaction card is tomaintain a high enough level of charge between transactions to ensurefunctionality of the transaction card. However, if there is an extendedperiod of time between the transaction card being used at a transactionterminal and/or if the components of the transaction card are used toofrequently between uses at a transaction terminal, the battery may runout of power and the functionality of the transaction card can be lost.Furthermore, a transaction card may be configured to have a standardsize. For example, financial transaction cards may be approximately 86millimeters (mm) by 54 mm by 0.75 mm. Accordingly, a size of the batteryof the transaction card is limited to a portion of those dimensions, andthus it may not be possible to enlarge a size of the battery to increasethe amount of power that can be stored by the battery.

Some examples described herein provide a charging device (which may bereferred to herein as a “charger”) for a transaction card that canenable the transaction card to be frequently charged without use of atransaction terminal and/or without increasing the size of a batterywithin the transaction card. The example charging device may providepower from a battery and/or may draw power from another device, such asa user device. In some implementations, the charging device may includea case that holds a user device, such that when the transaction card andthe user device are inserted or held by the charging device, a batteryof the transaction card can be charged using power from a battery of theuser device. In some implementations, the charging device may serve as asecurity apparatus to notify a user and/or a security system that thetransaction card is missing. For example, if the transaction card isremoved from the charging device for a threshold period of time, thecharging device and/or a user device in communication with the chargingdevice may notify a user and/or a security system that the transactioncard is missing. In such cases, one or more functions of the transactioncards may be disabled (e.g., by the security system) to preventunauthorized use of the card by an unauthorized user.

Therefore, some implementations described herein ensure that a batteryof a transaction card can maintain a charge between transactions attransaction terminals, and thus ensure that the transaction card hasfull functionality between the transactions at the transactionterminals. As such, communication resources, processing resources,and/or the like, that may otherwise be used to access or utilize afunction of the transaction card can be conserved. For example, if auser device or a transaction terminal is to attempt to access a paymenttoken from the transaction card, some implementations described hereincan ensure that the transaction card has power to provide the paymenttoken to the user device or the transaction terminal. In such a case,communication resources and/or processing resources of the user deviceand/or the transaction terminal can be conserved by ensuring that thetransaction card has enough power to provide the payment token andavoiding loss of functionality due to a lack of charging the batterybetween transactions at transaction terminals. Furthermore, processingand/or networking resources associated with recovering funds fromfraudulent activity can be conserved using one or more of the exampleimplementations described herein. For example, processing and/ornetworking resources used to recover funds from a transaction card thatwent missing and was undetected can be conserved using a charging deviceas described herein because the charging device can detect that thetransaction card was missing and cause one or more functions of thetransaction card to be disabled to prevent the fraudulent activity fromoccurring.

FIG. 1 is a diagram of an example implementation 100 described herein.In example implementation 100 of FIG. 1, a battery powered charger for atransaction card includes a charging slot, a charging terminal withinthe charging slot, and a hub. Further, example implementation 100includes a transaction card with an integrated circuit (IC) chip (e.g.,a EUROPAY®, MASTERCARD®, VISA® (EMV) chip) and a battery that powerscomponents of the transaction card. As shown in example implementation100, the transaction card may be inserted into the charging slot, suchthat the IC chip is in contact with the charging terminal, to enable abattery of the transaction card to be charged from a battery of thebattery powered charger.

In some implementations, the IC chip may serve an interface for anotherIC chip of the transaction card. For example, the IC chip may serve as aphysical interface (including a plurality of contact plates) to anotherIC chip on a printed circuit board (PCB) of the smart transaction card.In such cases, the IC chip may serve as a charging terminal for the PCBand/or the other IC chip on the PCB. Furthermore, in such cases, the ICchip may not include any processing capabilities (e.g., to perform atransaction similar to an EMV chip). Accordingly, the IC chip may serveas a physical interface for one or more components of the transactioncard.

As shown in FIG. 1, and by reference number 110, the batterypowered-charger is configured to charge the transaction card. In exampleimplementation 100, the charging slot may be a sleeve of the batterypowered charger that is configured to fit the transaction card. As such,the charging slot may be configured to be slightly larger than thetransaction card, such that the transaction card fits tightly within thecharging slot (e.g., to ensure that the transaction card does not fallout of the charging slot, to ensure a strong or solid contact betweenthe IC chip and the charging terminal, and/or the like). The chargingslot may be shaped such that when the transaction card is inserted intothe charging slot, the IC chip is aligned with the charging terminal.

The charging terminal is positioned within the charging slot to be incontact with the IC chip when the transaction card is fully insertedinto the charging slot. Accordingly, power can be supplied from abattery of the battery powered charger to the transaction card via thecharging terminal and the IC chip to charge the battery of thetransaction card. The charging terminal may include a supply contact anda ground contact. When the transaction card is fully inserted within thecharging slot, the supply contact is positioned to be in contact with asupply pad (e.g., a pad connected to a voltage supply of a circuit ofthe transaction card) of the IC chip and the ground contact ispositioned to be in contact with a ground pad (e.g., a ground of acircuit) of the IC chip. Accordingly, a battery of the transaction cardmay draw power via the supply pad and the ground pad of the IC chip whenthe IC chip is in contact with the charging terminal.

In some implementations, the hub of the battery powered charger mayinclude a battery and a switching component and/or processor tofacilitate charging the transaction card via the charging terminal. Thehub of the battery powered charger may be configured to communicate withone or more other devices (e.g., via a transceiver) that arecommunicatively coupled to the battery powered charger to facilitatecharging of the transaction card. For example, the hub may be configuredto communicate with the transaction card. In such a case, the hub mayrequest and/or obtain, from the transaction card, informationidentifying an amount of power remaining in the battery of thetransaction card. The hub may obtain such information via the chargingterminal and/or IC chip once the transaction card is inserted into thecharging slot. Additionally, or alternatively, the hub may obtain theinformation via a wireless communication (e.g., a short range wirelesscommunication, such as BLUETOOTH® communication, near fieldcommunication (NFC), and/or the like).

In some implementations, the hub of the battery powered charger may beconfigured as a dedicated device for charging the transaction card. Forexample, the battery of the battery powered charger and the switchingcomponent and/or the processor may be configured to only provide powerto the charging terminal. In such cases, the hub may not be configuredto establish a communication session with other devices or thetransaction card or may not be configured to perform other functionsthat are not related to charging a transaction card.

As further shown in FIG. 1, and by reference number 120, the batterypowered charger receives the transaction card in the card slot. Forexample, a user may insert the transaction card into the charging slotby sliding the transaction card into the charging slot. In someimplementations, the user may store the transaction card in the chargingslot between transactions at transaction terminals.

In some implementations, the battery powered charger may be includedwithin a wearable item and/or a wearable device. For example, thecharging slot and/or charging terminal may be integrated into an articleof clothing (e.g., shorts, pants, a shirt, a coat, under garments,and/or the like), a belt, a bag, a purse, a backpack, a wallet, a wristband, a sleeve, an arm strap, and/or the like. Furthermore, in someimplementations, the charging slot and/or charging terminal may beintegrated into the wearable device. For example, the charging slot maybe a pocket of the wearable device, may be included within a pocket ofthe wearable device, or may be included within a pocket of the wearabledevice. In such cases, the transaction card may be received via anopening in the pocket of the wearable device. Accordingly, in someimplementations, the user may insert the transaction card into awearable device worn on the user's person.

Once the transaction card is fully inserted into the charging slot, theIC chip of the transaction card (and/or one or more contacts of thetransaction card) is capable of receiving power from the battery poweredcharger.

As further shown in FIG. 1, and by reference number 130, the batterypowered charger may provide power to the transaction card via the ICchip and/or through contacts of an IC chip that are serving as aphysical interface for an IC chip of the transaction card, when the ICchip is in contact with the charging terminal. In some implementations,the hub may determine or identify that the IC chip is in contact withthe charging terminal based on a change in resistance between a supplycontact and a ground contact of the charging terminal (e.g., due to theresistance of the IC chip being applied to the charging terminal whilein contact with the charging terminal).

In some implementations, the battery powered charger provides power tothe transaction card constantly while the IC chip is in contact with thecharging terminal. Additionally, or alternatively, the battery poweredcharger provides power to the transaction card when an amount of powerremaining in the battery of the transaction card is less than athreshold level. For example, the hub may determine an amount of powerremaining in the battery of the transaction card. When the amount isless than a threshold level (e.g., 90% of capacity, 80% of capacity, 50%of capacity, and/or the like), the hub may provide power to thetransaction card to charge the battery until the amount of power in thebattery satisfies the threshold level (or another designated thresholdcharge level (e.g., max capacity, 90% capacity, and/or the like).Accordingly, the hub may determine and/or monitor the amount of power inthe battery of the transaction card.

In some implementations, the battery powered charger may notify a userthat the transaction card is fully charged. For example, the batterypowered charger may include a user interface (e.g., a display, anindicator light (e.g., a light emitting diode (LED)), a microphone,and/or the like) that notifies the user when the transaction card ischarged. Additionally, or alternatively, the battery powered charger mayindicate, via the user interface, a status of the charge of the batteryof the transaction card (e.g., whether the battery is currentlycharging, an amount of charge the battery has, and/or the like).

As described herein, the battery powered charger of exampleimplementation 100 may charge a transaction card received into acharging slot of the battery powered charger via the charging terminaland/or the IC chip of the transaction card. Therefore, the transactioncard can be charged, without the use of a transaction terminal and/orwithout performing a transaction via the transaction card.

As indicated above, FIG. 1 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 1.

FIG. 2 is a diagram of an example implementation 200 described herein.The example implementation 200 includes a charger case with atransaction card charging slot. The charger case can hold a user deviceand charge a battery of a transaction card inserted into the chargingslot (e.g., via a battery of the charger case and/or via a battery ofthe user device). As shown, the charger case includes a charging slot toreceive a transaction card (similar to the charging slot of FIG. 1), ahub (similar to the hub of FIG. 1), a charging jack, and a user deviceholder. In some implementations, the charger case may be configured toprotect the user device and/or prevent damage (e.g., scratches, cracks,and/or the like) to the user device.

The user device holder may be shaped and/or configured to hold a userdevice (e.g., a mobile phone, a personal digital assistant, a digitalmusic player, a gaming device, and/or the like). For example, internaldimensions of the user device holder may closely match externaldimensions of the user device such that the user device tightly fitsinto the user device holder. Accordingly, the charger case and/or userdevice holder can take various shapes to match dimensions of aparticular user device that the charger case is configured to hold. Insome implementations, the charger case is formed of a flexible materialthat can stretch to receive the user device and retract once the userdevice is inserted into the user device holder of the charger case totightly hold the user device in place.

The charging jack of the charger case may include any suitable interfaceor connector that is to be coupled with an interface or connector of theuser device when the user device is inserted into the user deviceholder. For example, the charging jack may include a connector (e.g., auniversal serial bus (USB) connector, a LIGHTNING® connector, and/or thelike) that communicatively couples the user device to the hub and/or tothe charging terminal of the charger case. Accordingly, the chargingjack may be any suitable connector that is configured to be coupled witha user device that fits in the user device holder of the charger case.In some implementations, the charger jack may be fixed in a position ofthe charger case such that charger jack is not flexible relative to thecharger case. Additionally, or alternatively, the charger jack mayinclude or be connected to a wire (e.g., a tether, a cord, and/or thelike) that attaches to the hub and/or the charging terminal of thecharger case to enable flexibility in the user device fitting within theuser device holder and/or connecting the user device to the hub and/orcharging terminal.

According to some implementations, dimensions of the charger case maycorrespond to dimensions of the transaction card and/or dimensions of auser device that is to be held in the charger case. For example, a widthof the charger case on a front side of the charger case (e.g., the sideof the charger case with the user device holder) may be the same as thewidth of the back side of the charger case (e.g., the side of thecharger case with the charging slot). In such an example, the mobilephone and transaction card may have the same and/or similar width (e.g.,within a threshold percentage).

As described herein, the charger case of example implementation 200and/or a user device inserted in the charger case may be configured tocharge a battery of a transaction card inserted into the charging slotof the charger case.

As indicated above, FIG. 2 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 2.

FIG. 3 is a diagram of an example implementation 300 described herein.In example implementation 300 of FIG. 3, a charger case is configured tocharge a transaction card via a battery of the charger case and/or abattery of a user device. In some implementations, the user device maybe configured to communicate with the charger case and/or thetransaction card. For example, the user device may include and/orexecute an application that enables the user device to accessinformation from the transaction card (e.g., a battery level of thetransaction card, an account number of the transaction card, a balanceassociated with the account of the transaction card, a user associatedwith the transaction card, a financial institution associated with thetransaction card, and/or the like) and/or the charger case (e.g., abattery level of a battery of the charger case, whether a transactioncard is inserted in the charger case, and/or the like).

As shown in FIG. 3, and by reference number 310, the user device isinserted into a holder of the charger case. For example, a user may fitthe user device into the charger case to enable the charger case tocharge the user device and/or enable the user device to charge atransaction card. Once within the charger case, the charging jack may becommunicatively coupled with a device interface (e.g., a connector) ofthe user device to enable the charger case (e.g., the hub of the chargercase) to draw power from the user device and/or communicate with theuser device.

As further shown in FIG. 3, and by reference number 320, a transactioncard is inserted into the charging slot of the charger case. Thetransaction card may be inserted similarly as when inserted into thecharging slot of example implementation 100. In some implementations,the transaction card may be inserted into the charging slot before theuser device is inserted into the user device holder of the charger case.

As further shown in FIG. 3, and by reference number 330, the user deviceand/or the charger case detect that the transaction card is insertedinto the charging slot and are configured to charge the transactioncard. Similar to the battery powered charger of example implementation100, the charger case (e.g., via the hub) may constantly or continuouslyprovide power to the transaction card when the transaction card iswithin the charging slot from a battery (e.g., a rechargeable battery)of the charger case (which may be referred to as a “charger battery”).Furthermore, the charger case and/or the user device may determine thatan amount of remaining power in a battery of the transaction card isless than a threshold level, cause power to be provided from the batteryof the charger case to the transaction card until an amount of power inthe battery of the transaction card satisfies a threshold level, and/orthe like. The charger case may cease providing power to the battery ofthe transaction card once a threshold level of power is reached in thebattery of the transaction card.

In some implementations, the charger case may be configured to providepower to a battery of the user device. For example, in response to arequest from the user device to provide power to the charger case (orbased on an amount of power remaining in a battery of the user devicereaching a threshold level), the user device may request the chargercase to provide power to the user device. The charger case may thenaccept or deny the request to provide power to the user device based onwhether an amount of power remaining in the battery satisfies athreshold level (e.g., 40% of capacity, 60% of capacity, and/or thelike). If the amount of power remaining satisfies the threshold level,the charger case may provide power to the user device to charge thebattery of the user device. On the other hand, if the amount of powerremaining in the battery does not satisfy the threshold level, thecharger case may not charge the battery of the user device.

In some implementations, the charger case (e.g., via the hub) mayrequest the user device to provide power to charge the battery of thetransaction card. For example, the charger case may identify that theuser device is within the user device holder and/or communicativelycoupled with the charging jack. The charger case may then request, viathe charging jack, the user device to provide the power to charge thebattery of the transaction card. In some implementations, the userdevice may accept or deny the request to provide the power to thecharger case based on an amount of remaining power in a battery of theuser device. For example, if the amount of power remaining in thebattery of the user device is less than a threshold level (e.g., 10% ofcapacity, 20% of capacity, 40% of capacity, 50% of capacity, and/or thelike), the user device may deny the request to provide power to thecharger case and/or the battery of the transaction card. Accordingly,the user device may preserve limited battery power to extend thefunctionality or lifetime of the user device. On the other hand, if theamount of power remaining in the battery is above the threshold level,the user device may accept the request to provide the power to thecharger case and/or battery of the transaction card.

Therefore, in some implementations, the charger case may await aresponse from the user device, and receive or draw the power from thebattery of the user device if the user device accepts the request toprovide the power. The charger case may then provide or forward thepower to the battery of the transaction card via the charging terminaland IC chip of the transaction card. Additionally, or alternatively, thecharger case (e.g., via the hub), may use the power from the battery ofthe user device to charge a battery of the charger case. The chargercase may then use the power from the battery of the charger case tocharge the battery of the transaction card.

In some implementations, the charger case may wait to request that theuser device provide power to charge the battery of the transaction carduntil an amount of power in the battery of the charger case is less thana threshold level. For example, the charger case may determine that anamount of remaining power in the battery of the charger case is lessthan a threshold level and request the user device to provide powerand/or draw power from the battery of the user device based ondetermining that the amount of remaining power in the charger battery isless than the threshold level. In some implementations, if the chargercase determines that the amount of remaining power in the charger caseis equal to or greater than the threshold level, then the charger casemay charge the battery of the transaction card using power from thebattery of the charger case.

In some implementations, the charger case may notify a user that thetransaction card is fully charged. For example, the charger may includea user interface that notifies the user and/or may use the userinterface of the user device to notify the user when the transactioncard is charged. Additionally, or alternatively, the charger case mayindicate, via the user interface of the case or the user interface ofthe user device, a status of the charge of the battery of thetransaction card (e.g., whether the battery is currently charging, anamount of charge the battery has, and/or the like).

Accordingly, the charger case of example implementation 300 may enable abattery of a transaction card to be charged from a battery of thecharger case and/or a battery of the user device held in the chargercase.

As indicated above, FIG. 3 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 3.

FIG. 4 is a diagram of an example implementation 400 described herein.In example implementation 400, a security system may be used to disablefunctionality of a transaction card if the transaction card is removedfrom a charging slot of a charging device (shown as a charger case inFIG. 4) for a threshold period of time.

As shown in FIG. 4, and by reference number 410, a transaction card isremoved from the charging slot. For example, a user may remove thetransaction card to use the transaction card at a transaction terminal.In some implementations, the charger case and/or the user device maydetermine that the transaction card has been removed from the chargingslot based on the IC chip no longer being in contact with the chargingterminal. For example, the charger case and/or the user device maydetect a change in a resistance between a supply contact and a groundcontact of the charging terminal (e.g., due to the resistance of thetransaction card being removed when the IC chip is no longer in contactwith the charging terminal).

As further shown in FIG. 4, and by reference number 420, the user devicenotifies a backend system that the transaction card has been removed fora threshold period of time. In some implementations, the charger casemay notify the user device that the transaction card has been removedfrom the charging slot for the threshold period of time (e.g., 10minutes, 20 minutes, 1 hour, and/or the like). In some implementations,the charger case may notify the user device to alert the user that thetransaction card is missing. For example, the charger case may send anotification that causes the user device display an alert, sound analarm, and/or the like. As such, the user may be notified that thetransaction card is missing or not included within the charging slot.

Additionally, or alternatively, the user device may monitor the chargingterminal and identify that the transaction card has been removed fromthe charging slot for the threshold period of time. The user device maysimilarly alert the user (e.g., via a user interface of the user device)that the transaction card has been removed after the threshold period oftime expires.

As further shown in FIG. 4, and by reference number 430, the securitysystem disables a function of the transaction card. For example, thesecurity system may enable and/or disable functions (e.g., an ability touse the transaction card in a transaction, such as to pay for a productor service, access a secure location, record a loyalty purchase, redeema reward, access features of the transaction card, access an account ofthe transaction card, and/or the like) of the transaction card based onthe status of the transaction card (e.g., whether the transaction cardis active or inactive, whether the transaction card is valid or invalid,whether an account associated with the transaction card is in goodstanding or not, and/or the like). As such, when the transaction card isin a known location (e.g., within the charging slot of the chargercase), the security system may enable functionality of the transactioncard and when the transaction card is in an unknown location (for athreshold period of time), the security system may disable functionalityof the transaction card.

According to some implementations, if the transaction card is removedfrom the charging slot and returned to the charging slot within thethreshold period of time, the charger case and/or user device may notalert the user and/or may not notify the security system to disable thefunctionality of the transaction card. In some implementations, if thetransaction card is returned to the charging slot after the thresholdperiod of time, the charger case and/or user device may communicate withthe security system to restore the functionality of the transactioncard. For example, the security system may perform a verification withthe user device and/or charger case to ensure that the transaction cardis in the possession of an authorized user of the account. In suchcases, the security system may verify the transaction card is in thepossession of an authorized user via the user device by requiring a userof the user device to answer security questions, by performing asecondary authentication process, and/or the like.

Accordingly, the charger case and/or user device may be used as asecurity system to monitor the presence of the transaction card andensure that the transaction card is not lost or stolen. Accordingly,some implementation describe herein may conserve resources with respectto recovering from fraudulent transactions that may have otherwise haveoccurred.

As indicated above, FIG. 4 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 4.

FIG. 5 is a diagram of an example environment 500 in which systemsand/or methods, described herein, may be implemented. As shown in FIG.5, environment 500 may include a transaction card 510, a charging device520, a user device 530, a network 540, a backend system 550, and atransaction terminal 560. Devices of environment 500 may interconnectvia wired connections, wireless connections, or a combination of wiredand wireless connections.

Transaction card 510 includes a transaction card capable ofcommunicating with the components of environment 500 (e.g., viaBluetooth communication, BLE communication, Wi-Fi communication, NFCsession, and/or the like). Transaction card 510 is capable ofcommunicating data for a transaction with transaction terminal 560. Forexample, transaction card 510 may communicate data including atransaction token, transaction card identification information (e.g., anaccount identifier, a cardholder identifier, and/or the like), accountinformation, banking information, transaction information (e.g., atransaction token), and/or the like. For example, to communicate thedata, transaction card 510 may include a magnetic strip and/or anintegrated circuit (IC) chip (e.g., a EUROPAY®, MASTERCARD®, VISA® (EMV)chip). Transaction card 510 may include an antenna to communicate dataassociated with transaction card 510. The antenna may be a passive RFantenna, an active RF antenna, and/or a battery-assisted RF antenna.Transaction card 510 may correspond to the transaction cards of FIGS.1-4. As described herein, a battery of transaction card 510 may becharged by charging device 520.

Charging device 520 includes a device capable of providing power totransaction card 510. Charging device 520 may include a battery, aswitching component, a processor, and/or the like to facilitate charginga transaction card via the IC chip and/or through contacts of thetransaction card. For example, charging device 520 may correspond and/orby implemented by the battery powered charger of FIG. 1 and/or thecharger case of FIGS. 2-4. According to some implementations, chargingdevice 520 is not configured to facilitate processing a transaction (asperformed by transaction terminal 560).

User device 530 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information associatedwith charging transaction card 510 in accordance with someimplementations herein. For example, user device 530 may include acommunication device and/or computing device, such as a mobile phone(e.g., a smart phone, a radiotelephone, and/or the like), a personaldigital assistant, a digital music player, a gaming device, a wearablecommunication device (e.g., an electronic wallet device, and/or thelike), or a similar type of device.

Network 540 includes one or more wired and/or wireless networks. Forexample, network 540 may include a cellular network (e.g., a long-termevolution (LTE) network, a code division multiple access (CDMA) network,a 3G network, a 4G network, a 5G network, another type of nextgeneration network, etc.), a public land mobile network (PLMN), a localarea network (LAN), a wide area network (WAN), a metropolitan areanetwork (MAN), a telephone network (e.g., the Public Switched TelephoneNetwork (PSTN)), a private network, an ad hoc network, an intranet, theInternet, a fiber optic-based network, a cloud computing network, or thelike, and/or a combination of these or other types of networks.

Backend system 550 includes one or more devices capable of authorizingand/or facilitating a transaction. For example, backend system 550 mayinclude one or more servers and/or computers to store and/or provideinformation (e.g., authorizations, balances, transaction tokens,security information, account information, and/or the like) associatedwith processing a transaction via transaction terminal 560.

Backend system 550 may include one or more devices associated withfinancial institutions (e.g., banks, credit unions, and/or the like)and/or transaction card associations that authorize a transaction and/orfacilitate a transfer of funds or payments between an account of acardholder of transaction card 510 and an account of an individual orbusiness of transaction terminal 560. For example, backend system 550may include one or more devices of one or more issuing financialinstitutions associated with transaction card 510, one or more devicesof one or more acquiring financial institutions (or merchant banks)associated with transaction terminal 560, and/or one or more devicesassociated with one or more card associations (e.g., VISA®, MASTERCARD®,and/or the like) associated with transaction card 510. Accordingly, inresponse to receiving transaction card data associated with transactioncard 510 from transaction terminal 560, various financial institutionsand/or card associations of backend system 550 may communicate toauthorize the transaction and/or transfer funds between the accountsassociated with transaction card 510 and/or transaction terminal 560.

Backend system 550 may include one or more devices associated withsecuring financial information and/or data associated with an account oftransaction card 510. For example, backend system 550 may have theability to enable and/or disable one or more functions of transactioncard 510. For example, a security system of backend system 550 candeactivate transaction capabilities of transaction card 510 orreactivate transaction capabilities of transaction card 510 based onwhether or not transaction card is in a charging slot of charging device520, as described herein.

Transaction terminal 560 includes one or more devices capable ofreceiving, generating, storing, processing, and/or providing informationassociated with facilitating processing a transaction (a PoStransaction). For example, transaction terminal 560 may include acommunication device and/or computing device capable of receiving datafrom transaction card 510 and processing a transaction based on thedata. In some implementations, transaction terminal 560 may include adesktop computer, a laptop computer, a tablet computer, a handheldcomputer, and/or the like. Transaction terminal 560 may be owned and/oroperated by one or more individuals or businesses engaged in a sale ofgoods or services (e.g., one or more merchants, vendors, serviceproviders, and/or the like). Transaction terminal 560 may include a PoSterminal, a security access terminal, an ATM terminal, and/or the like.

The number and arrangement of devices and networks shown in FIG. 5 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 5. Furthermore, two or more devices shown in FIG. 2 may beimplemented within a single device, or a single device shown in FIG. 5may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 500 may perform one or more functions described as beingperformed by another set of devices of environment 500.

FIG. 6 is a diagram of example components of a device 600. Device 600may correspond to transaction card 510, charging device 520, user device530, backend system 550, and/or transaction terminal 560. In someimplementations, transaction card 510, charging device 520, user device530, backend system 550, and/or transaction terminal 560 may include oneor more devices 600 and/or one or more components of device 600. Asshown in FIG. 6, device 600 may include a bus 610, a processor 620, amemory 630, a storage component 640, an input component 650, an outputcomponent 660, and a communication interface 670.

Bus 610 includes a component that permits communication among thecomponents of device 600. Processor 620 is implemented in hardware,firmware, or a combination of hardware and software. Processor 620 is acentral processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), a microprocessor, a microcontroller,a digital signal processor (DSP), a field-programmable gate array(FPGA), an application-specific integrated circuit (ASIC), or anothertype of processing component. In some implementations, processor 620includes one or more processors capable of being programmed to perform afunction. Memory 630 includes a random access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 620.

Storage component 640 stores information and/or software related to theoperation and use of device 600. For example, storage component 640 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 650 includes a component that permits device 600 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 650 mayinclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 660 includes a component that providesoutput information from device 600 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 670 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 600 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 670 may permit device 600to receive information from another device and/or provide information toanother device. For example, communication interface 670 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface, orthe like.

Device 600 may perform one or more processes described herein. Device600 may perform these processes based on processor 620 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 630 and/or storage component 640. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 630 and/or storagecomponent 640 from another computer-readable medium or from anotherdevice via communication interface 670. When executed, softwareinstructions stored in memory 630 and/or storage component 640 may causeprocessor 620 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 6 are provided asan example. In practice, device 600 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 6. Additionally, or alternatively, aset of components (e.g., one or more components) of device 600 mayperform one or more functions described as being performed by anotherset of components of device 600.

FIG. 7 is a flow chart of an example process 700 associated with abattery charger for transaction card. In some implementations, one ormore process blocks of FIG. 7 may be performed by a charging device(e.g., charging device 520). In some implementations, one or moreprocess blocks of FIG. 7 may be performed by another device or a groupof devices separate from or including charging device (e.g., chargingdevice 520), such as a transaction card (e.g., transaction card 510), auser device (e.g., user device 530), or a backend system (e.g., backendsystem 550).

As shown in FIG. 7, process 700 may include detecting a transaction cardis received within a charging slot (block 710). For example, thecharging device (e.g., using processor 620, input component 650,communication interface 670, and/or the like) may detect the transactioncard is received within the charging slot, as described above.

As shown in FIG. 7, process 700 may include determining that an amountof remaining power in a charger battery is less than a first thresholdlevel (block 720). For example, the charging device (e.g., usingprocessor 620, input component 650, communication interface 670, and/orthe like) may determine that the amount of remaining power in thecharger battery is less than the first threshold level, as describedabove.

As shown in FIG. 7, process 700 may include requesting a user device toprovide power to charge the transaction card based on determining theamount of remaining power in the charger battery is less than the firstthreshold level, wherein the user device is communicatively coupled tothe charging device via a device interface of the user device and acharging jack of the charging device (block 730). For example, thecharging device (e.g., using processor 620, memory 630, storagecomponent 640, input component 650, output component 660, communicationinterface 670, and/or the like) may request a user device to providepower to charge the transaction card based on determining the amount ofremaining power in the charger battery is less than the first thresholdlevel, as described above. In some implementations, the user device iscommunicatively coupled to the charging device via a device interface ofthe user device and a charging jack of the charging device.

As shown in FIG. 7, process 700 may include receiving the power from abattery of the user device (block 740). For example, the charging device(e.g., using processor 620, input component 650, communication interface670, and/or the like) may receive the power from a battery of the userdevice, as described above.

As shown in FIG. 7, process 700 may include providing the power to thetransaction card to charge a battery of the transaction card via acharging terminal of the charging device (block 750). For example, thecharging device (e.g., using processor 620, output component 660,communication interface 670, and/or the like) may provide the power tothe transaction card to charge a battery of the transaction card via acharging terminal of the charging device, as described above.

Process 700 may include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In some implementations, the charging device is included within a casethat holds the user device. In some implementations, detecting thetransaction card is received within the charging slot may includeidentifying that an integrated circuit (IC) chip of the transaction cardis in contact with the charging terminal of the charging device, anddetecting the transaction card is received within the charging slot ofthe charging device based on identifying that the IC chip is in contactwith the charging terminal. In some implementations, detecting thetransaction card is received within the charging slot may includeidentifying that one or more contacts of the transaction card is incontact with the charging terminal of the charging device and detectingthe transaction card is received within the charging slot of thecharging device based on identifying that the one or more contacts ofthe transaction card are in contact with the charging terminal. In someimplementations, an integrated circuit (IC) chip of the transaction cardis powered by the power provided to the transaction card.

In some implementations, the user device may include a mobile phone, apersonal digital assistant, a digital music player, or a gaming console.In some implementations, the charging jack is configured to be insertedinto the device interface of the user device when the user device isinserted within a case of the charging device, wherein the case of thecharging device is configured to hold the user device.

In some implementations, the charging device may determine that anamount of power in the battery of the transaction card is less than asecond threshold level, wherein the user device is requested to providethe power to charge the transaction card based on determining that theamount of power in the battery of the transaction card is less than thesecond threshold level. In some implementations, the charging device,after providing the power to the transaction card, may determine that anamount of power in the battery of the transaction card satisfies asecond threshold level and cease providing the power to the transactioncard.

In some implementations, the power is provided to the transaction cardvia an integrated circuit (IC) chip of the transaction card that is incontact with the charging terminal.

Although FIG. 7 shows example blocks of process 700, in someimplementations, process 700 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 7. Additionally, or alternatively, two or more of theblocks of process 700 may be performed in parallel.

FIG. 8 is a flow chart of an example process 800 associated with abattery charger for a transaction card. In some implementations, one ormore process blocks of FIG. 8 may be performed by a charging device(e.g., charging device 520). In some implementations, one or moreprocess blocks of FIG. 8 may be performed by another device or a groupof devices separate from or including charging device (e.g., chargingdevice 520), such as a transaction card (e.g., transaction card 510), auser device (e.g., user device 530), and a backend system (e.g., backendsystem 550).

As shown in FIG. 8, process 800 may include detecting that a transactioncard is received within the charging slot (block 810). For example, thecharging device (e.g., using processor 620, input component 650,communication interface 670, and/or the like) may detect that atransaction card is received within the charging slot, as describedabove.

As shown in FIG. 8, process 800 may include drawing power from a batteryof the user device to provide power to the transaction card (block 820).For example, the charging device (e.g., using processor 620, inputcomponent 650, communication interface 670, and/or the like) may drawpower from a battery of the user device to provide power to thetransaction card, as described above.

As shown in FIG. 8, process 800 may include providing the power to thetransaction card via an integrated circuit (IC) chip that is in contactwith the charging terminal (block 830). For example, the charging device(e.g., using processor 620, memory 630, storage component 640, inputcomponent 650, output component 660, communication interface 670, and/orthe like) may provide the power to the transaction card via anintegrated circuit (IC) chip that is in contact with the chargingterminal, as described above.

Process 800 may include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In some implementations, the charging device may include a chargerbattery and the charging device may, prior to drawing power from thebattery of the user device, determine that an amount of remaining powerin the charger battery is less than a threshold level and draw powerfrom the battery of the user device based on determining that the amountof remaining power in the charger battery is less than the thresholdlevel. In some implementations, the user device is a mobile phone. Insome implementations, the IC chip includes one or more contactsconfigured to provide the power to one or more components of thetransaction card.

In some implementations, the charging device may request, via thecharging jack, the user device to provide the power to charge thetransaction card, wherein the battery provides power to one or morecomponents of the user device. In some implementations, the chargingdevice may determine that an amount of power remaining in a battery ofthe transaction card is less than a threshold level and draw the powerfrom the battery based on determining that the amount of power remainingin the battery of the transaction card is less than the threshold level.In some implementations, the charging device, when detecting that thetransaction card is received within the charging slot, may identify thatthe integrated circuit (IC) chip of the transaction card is in contactwith the charging terminal based on a change in resistance between asupply contact and a ground contact of the charging terminal and detectthe transaction card is received within the charging slot based onidentifying that the IC chip is in contact with the charging terminal.

Although FIG. 8 shows example blocks of process 800, in someimplementations, process 800 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 8. Additionally, or alternatively, two or more of theblocks of process 800 may be performed in parallel.

FIG. 9 is a flow chart of an example process 900 associated with abattery charger for transaction card. In some implementations, one ormore process blocks of FIG. 9 may be performed by a charging device(e.g., charging device 520). In some implementations, one or moreprocess blocks of FIG. 9 may be performed by another device or a groupof devices separate from or including charging device (e.g., chargingdevice 520), such as a transaction card (e.g., transaction card 510), auser device (e.g., user device 530), and a backend system (e.g., backendsystem 550).

As shown in FIG. 9, process 900 may include detecting a transaction cardis received within a charging slot when an integrated circuit (IC) chipof the transaction card is in contact with a charging terminal (block910). For example, the charging device (e.g., using processor 620, inputcomponent 650, communication interface 670, and/or the like) may detecta transaction card is received within a charging slot when an integratedcircuit (IC) chip of the transaction card is in contact with a chargingterminal, as described above.

As shown in FIG. 9, process 900 may include requesting a user device toprovide power to charge the transaction card via the charging terminal,wherein the user device is communicatively coupled to the chargingterminal (block 920). For example, the charging device (e.g., usingprocessor 620, component 660, communication interface 670, and/or thelike) may request a user device to provide power to charge thetransaction card via the charging terminal, wherein the user device iscommunicatively coupled to the charging terminal, as described above.

As shown in FIG. 9, process 900 may include receiving the power from theuser device (block 930). For example, the charging device (e.g., usingprocessor 620, input component 650, communication interface 670, and/orthe like) may receive the power from the user device, as describedabove.

As shown in FIG. 9, process 900 may include providing the power to thetransaction card to charge a battery of the transaction card (block940). For example, the charging device (e.g., using processor 620,output component 660, communication interface 670, and/or the like) mayprovide the power to the transaction card to charge a battery of thetransaction card, as described above.

Process 900 may include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In some implementations, the charging device may detect that thetransaction card has been removed from the charging slot based on the ICchip not being in contact with the charging terminal and send anotification to the user device that the transaction card has beenremoved from the charging slot to enable the user device to stopproviding power. In some implementations, the notification is configuredto cause the user device to alert, via a user interface of the userdevice, that the transaction card has been removed. In someimplementations, the notification is configured to cause the user deviceto alert a security system that is to disable a function of thetransaction card unless the transaction card is returned to the chargingslot within a threshold period of time.

In some implementations, the charging device may detect that thetransaction card has been removed from the charging slot based on the ICchip not being in contact with the charging terminal and, after athreshold period of time, send a notification to a security system tocause the security system to disable a function of the transaction card.In some implementations, the user device is held within a user devicecase that includes one or more processors of the charging device.

Although FIG. 9 shows example blocks of process 900, in someimplementations, process 900 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 9. Additionally, or alternatively, two or more of theblocks of process 900 may be performed in parallel.

Accordingly, as described herein, a charging device may charge atransaction card when the transaction card is within a charging slot ofthe charging device. The charging device may enable a battery of thetransaction card to be charged between transactions at transactionterminals. Furthermore, in some implementations, the charging device maynotify a user device and/or security system that the transaction cardhas been removed from the charging device. As such, the user deviceand/or security system may determine that the transaction card ismissing and/or disable one or more functions of the transaction card toprevent any unauthorized use of the transaction card.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Some implementations are described herein in connection with thresholds.As used herein, satisfying a threshold may refer to a value beinggreater than the threshold, more than the threshold, higher than thethreshold, greater than or equal to the threshold, less than thethreshold, fewer than the threshold, lower than the threshold, less thanor equal to the threshold, equal to the threshold, or the like.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and may be used interchangeably with “one ormore.” Where only one item is intended, the term “one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method, comprising: detecting, by a chargingdevice, an integrated circuit (IC) chip of a transaction card is nolonger in contact with a charging terminal of the charging device;determining, by the charging device and based on detecting the IC chipis no longer in contact with the charging terminal, the transaction cardhas been removed from a charging slot of the charging device;determining, by the charging device, that the transaction card has beenremoved from the charging slot for a threshold period of time; andproviding, by the charging device, a user device with data indicatingthat the transaction card has been removed from the charging slot forthe threshold period of time.
 2. The method of claim 1, furthercomprising: providing the user device with data that causes the userdevice to display an alert indicating that the transaction card has beenremoved from the charging slot.
 3. The method of claim 1, furthercomprising: causing an audible alarm to sound based on determining thatthe transaction card has been removed from the charging slot for thethreshold period of time; or providing the user device with data thatcauses the user device to make an audible alarm based on determiningthat the transaction card has been removed from the charging slot forthe threshold period of time.
 4. The method of claim 1, whereindetecting the IC chip is no longer in contact with the charging terminalcomprises: detecting a change in a resistance between a supply contactand a ground contact of the charging terminal; and determining that theIC chip is no longer in contact with the charging terminal based ondetecting the change in the resistance.
 5. The method of claim 1,wherein the charging device is communicatively coupled to the userdevice via a device interface of the user device and a charging jack ofthe charging device.
 6. The method of claim 1, wherein the user devicenotifies a backend system that the transaction card has been removed forthe threshold period of time.
 7. The method of claim 1, furthercomprising: providing a transaction server device with data that causesthe transaction card to be disabled based on determining that thetransaction card has been removed from the charging slot for thethreshold period of time.
 8. A device, comprising: one or more memories;and one or more processors communicatively coupled to the one or morememories, configured to: detect an integrated circuit (IC) chip of atransaction card is no longer in contact with a charging terminal of thedevice; determine, based on detecting the IC chip is no longer incontact with the charging terminal, the transaction card has beenremoved from a charging slot of the device; determine that thetransaction card has been removed from the charging slot for a thresholdperiod of time; and provide a user device with data indicating that thetransaction card has been removed from the charging slot for thethreshold period of time.
 9. The device of claim 8, wherein the one ormore processors are further configured to: provide the user device withdata that causes the user device to display an alert indicating that thetransaction card has been removed from the charging slot.
 10. The deviceof claim 8, wherein the one or more processors are further configuredto: cause an audible alarm to sound based on determining that thetransaction card has been removed from the charging slot for thethreshold period of time; or provide the user device with data thatcauses the user device to make an audible alarm based on determiningthat the transaction card has been removed from the charging slot forthe threshold period of time.
 11. The device of claim 8, wherein the oneor more processors, when detecting the IC chip is no longer in contactwith the charging terminal, are configured to: detect a change in aresistance between a supply contact and a ground contact of the chargingterminal; and determine that the IC chip is no longer in contact withthe charging terminal based on detecting the change in the resistance.12. The device of claim 8, wherein the device is communicatively coupledto the user device via a device interface of the user device and acharging jack of the device.
 13. The device of claim 8, wherein the userdevice notifies a backend system that the transaction card has beenremoved for the threshold period of time.
 14. The device of claim 8,wherein the one or more processors are further configured to: provide atransaction server device with data that causes the transaction card tobe disabled based on determining that the transaction card has beenremoved from the charging slot for the threshold period of time.
 15. Anon-transitory computer-readable medium storing instructions, theinstructions comprising: one or more instructions that, when executed byone or more processors of a charging device, cause the one or moreprocessors to: detect an integrated circuit (IC) chip of a transactioncard is no longer in contact with a charging terminal of the chargingdevice; determine, based on detecting the IC chip is no longer incontact with the charging terminal, the transaction card has beenremoved from a charging slot of the charging device; determine that thetransaction card has been removed from the charging slot for a thresholdperiod of time; and provide a user device with data indicating that thetransaction card has been removed from the charging slot for thethreshold period of time.
 16. The non-transitory computer-readablemedium of claim 15, wherein the one or more instructions, when executedby the one or more processors, further cause the one or more processorsto: provide the user device with data that causes the user device todisplay an alert indicating that the transaction card has been removedfrom the charging slot.
 17. The non-transitory computer-readable mediumof claim 15, wherein the one or more instructions, when executed by theone or more processors, further cause the one or more processors to:cause an audible alarm to sound based on determining that thetransaction card has been removed from the charging slot for thethreshold period of time; or provide the user device with data thatcauses the user device to make an audible alarm based on determiningthat the transaction card has been removed from the charging slot forthe threshold period of time.
 18. The non-transitory computer-readablemedium of claim 15, wherein the one or more instructions, that cause theone or more processors to detect the IC chip is no longer in contactwith the charging terminal, cause the one or more processors to: detecta change in a resistance between a supply contact and a ground contactof the charging terminal; and determine that the IC chip is no longer incontact with the charging terminal based on detecting the change in theresistance.
 19. The non-transitory computer-readable medium of claim 15,wherein the charging device is communicatively coupled to the userdevice via a device interface of the user device and a charging jack ofthe charging device.
 20. The non-transitory computer-readable medium ofclaim 15, wherein the user device notifies a backend system that thetransaction card has been removed for the threshold period of time.